eXtremeDB Sequence Error Codes
The following non-fatal return codes are specific to sequence storage and iterator processing. Sequence functions can also propagate general status, transaction, type, parameter, and memory errors.
Mnemonic constant
Value
Meaning and typical cause
MCO_E_SEQ_OUT_OF_ORDER
700
An append, insert, or store operation would violate an
asc or desc field declaration.MCO_E_SEQ_BOUNDED
701
An input iterator is already bound to another lazy operation while iterator binding checks are enabled. Build a second source iterator or use an explicit tee operation.
MCO_E_SEQ_LENGTH_MISMATCH
702
An operation that requires aligned inputs received sequences with different logical lengths.
MCO_E_SEQ_NULL_VALUE
703
A scalar getter encountered a NULL element, or an operation that cannot accept NULL values received one. Nullable getters return the NULL bitmap explicitly.
MCO_E_SEQ_NOT_ORDERED
704
An ordered-only search operation was requested for a sequence without ascending or descending order.
Reserved
705-799
Reserved for sequence return codes.
Related status codes
MCO_S_CURSOR_ENDindicates normal iterator exhaustion.MCO_S_NOTFOUNDcommonly indicates an empty stored sequence, an empty search range, or an absent lookup value.MCO_E_ACCESSis returned when a field-modifying operation is used from a read-only transaction.MCO_E_ILLEGAL_TYPEindicates an incompatible iterator element type.MCO_E_ILLEGAL_PARAMindicates an invalid position or another invalid argument.
See Iterator Lifecycle, Ownership, and Errors and Generated Sequence Field Functions for operation-specific contracts.
Related Topics